home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Power Tools 1993 November - Disc 2
/
Power Tools Plus (Disc 2 of 2)(November 1993)(HP).iso
/
hotlines
/
nethl
/
ots
/
txt.cpy
/
SCRIPT.TXT
< prev
next >
Wrap
Text File
|
1993-08-04
|
9KB
|
222 lines
OTS/9000 Slide Script
---------------------
Note :
This package contains the OTS presentation slides and script.
In order to get the slides, transfer the slide file to a PC,
rename it OTS.EXE and execute it.
Slide 1 :
Cover slide.
OTS 9000 is the pillar for distributed applications using OSI
Standards.
Slide 2 :
Slide 2 and 3 are targeted to an audience of integrators / VARs.
Explain criterias commonly used when selecting a platform.
Slide 3 :
Explains additional criterias used when dealing with OSI.
Slide 4 :
This slide presents the situations where customers are using an OSI
stack. It also presents the situation where we' ve been successfull
selling OTS/9000.
X400 and FTAM are not present on the slide. The idea here is to
concentrate on OTS/9000 and its APIs. Of course, we' re selling OTS
with X400 and FTAM as well.
Slide 5 :
Introduces OTS/9000 (part numbers). Stresses the fact that OTS/9000
is available, with the same API, over all HP/9000 platforms. Hence
OTS/9000, and HP/9000 can accomodate applications with various
performance, connectivity requirements. Also, upward migration path
for growing applications is guaranteed.
Slide 6 :
Illustrates use of OTS/9000 in Network Surveillance Applications. Key
benefits of OTS/9000 are availability of multiple APIs (Transport,
Session, ACSE/ROSE/Presentation, CMISE [ as a separate product ! ])
-----------------------
and high number of supported connections (up to 448).
References here are system integrators for the Telecom industry.
Germany : Ongoing project within HP for German Telecom.
Contact : Peter Palatinus/ Rudiger Barz.
Slide 7 :
OTS/9000 in manufacturing environment. Can be used with and without
MMS. Key benefits are use of 802.3 and ENV 41101 profiles, together
with the support of 2 LAN cards for redundancy reasons.
Germany : Ongoing project with Siemens for GM/Opel.
Contact : Franz Koppold (Germany)
France : Ongoing project with GEC_Alsthom
Contact : Ian Bromehead (France)
Slide 8 :
OTS/9000 can be used to communicate with mainframes using OSI as their
native communication architecture. This usually requires working with
third_parties to provide for the proprietary upper services, like
terminal emulation, file transfer.
Siemens : Third parties are Conware and Coconet.
Contact : Walter Hestler in Boeblingen. References available
from Walter.
Bull : Contact :
* Spain : Jose Cea in Madrid.
Third party : Gallagher and Robertson.
Reference : Pilote site running. See Jose.
* France : Solofo Rafeno (Evry).
Slide 9 :
Introduces major OTS/9000 features in regard of OSI services.
Use OTS/9000 data sheet as complement.
Slide 10 :
OTS/9000 architecture overview.
OTS/9000 is now integrated in the Streams kernel programming
environment.
Streams is the leading environment for writing advanced drivers,
selected by AT&T and OSF.
Major benefits: * Transport connection endpoint in XTI now maps onto a
HP_UX file descriptor.
* Performance. Performance over LAN on Nova similar
to TCP/IP performance (> 800 kbytes/second)
Detailed performance figures available from the factory (contact ENMC)
Note/mention that OTS/9000 coexists with TCP/IP in the HP_UX kernel.
Slide 11 :
Introduces OTS/9000 application development environment.
. APIs are fully documented with programming example.
. Available chain of expertise within HP to help the customers build
their applications.
. Standard HP CASE tools and support available.
Slide 12 :
Presents the OTS/9000 Application Programming Interfaces (APIs).
Refer to OTS/9000 data sheet for more details.
Slide 13 :
OTS/9000 configuration.
One of the major complaints regarding former OTS/9000 versions was the
lack of dynamic configuration. OTS/9000 C.03.00 addresses this need by
making most of the stack parameters dynamically configurable.
Dynamic configuration can be achieved either by invoking the Routing
Information Base management commands [ Add / Delete / View routing
entries ] or by editing the ASCII configuration files and then
invoking "otsupdate".
The arrows in RED depict the start_up configuration process. The
ASCII configuration files are read and configuration information is
communicated to the stack [ via OTSSTART ].
The arrows in GREEN depict the dynamic configuration process after
OTS/9000 start up. Routing management commands directly impact the
stack Routing Information Base. As an option, the same commands may,
if needed, impact the Routing Information stored in ASCII
configuration files. Hence, the dynamic Routing Base modifications
can be recorded for the next OTS/9000 start up.
Slide 14 :
OTS/9000 troubleshooting tools.
OSIDIAG is the major tool for troubleshooting OTS/9000 installation
and connectivity problems. OSIDIAG can be invoked for every OSI
service supported by OTS/9000.
With OSIDIAG and NETTL/NETFMT, OTS/9000 is as well integrated within
HP_UX than TCP/IP is [ "ping" would be the OSIDIAG equivalent ].
Slide 15 :
Interoperability (IOP) strategy.
The "official" IOP databases only deal with X400 and FTAM for now.
HP' s X400 and FTAM both use OTS/9000. Therefore official IOP records
for X400 and FTAM can be used for OTS/9000.
Slide 16 :
Functional profiles supported by OTS/9000.
Most important ones in Europe are CEN/CENELEC profiles.
Among these profiles, ENV 41101 (manufacturing and Siemens
connectivity), ENV 41104 (TP0/2 over X25) and ENV 41102 (TP4 over LAN)
are the most widely used in Europe.
PICS completed to date:
Session: COS session version 1.0 (MHS)
COS session version 2.0 (FTAM)
CTS-WAN (OSTC) PICS
CTS-WAN (OSTC) session version 1.0 (MHS)
INTAP (MHS) PICS
INTAP (FTAM) PICS
Transport/
CLNP: COS: TP4, CLNP (TA51, TA52, TA1111
profiles)
COS: TP0 (TD1111 profile)
US GOSIP 1.0: TP0, TP4, CLNP PICS
CTS-WAN PICS: TP0, 1, 2, 3, 4
CTS-WAN (MHS) PICS
INTAP PICS: TP0, 2
UK GOSIP PICS: TP0, 2, 4, CLNP, ES-IS
Australian GOSIP PICS: TP0, 2, 4, CLNP
Slide 17, 18 :
HP's Conformance Test Center (CTC) is located in IND, Cupertino,
California, USA. Since November 1990 the CTC has operated as a
NVLAP (U.S. accreditation body) accredited first party OSI
conformance test center. The scope of accreditation covers FTAM,
X.400, TP4, TP0, CLNP, and X.25. The test center uses the IDACOM
tester for X.25 and NCC testers for all other areas. All of these
testers have been validated by OSTC.
Also HP has applied to RNE (Reseau National D'Essais, the French
accreditation body) for accreditation of HP's Conformance Test Center
(CTC). The application has been favorably received and we are
currently preparing for the accreditation. The HP Conformance Test
Center intends to request accreditation for the following areas:
FTAM, X.400, Session, TP4, TP0, and CLNP. With RNE accreditation,
Protocol Conformance Test Reports (PCTRs) produced at the CTC can be
submitted to certification agencies in Europe for obtaining
Certificates of Conformity, if necessary.
Slide 19 :
Product evolution.
This slide shows continued increases in functionality with each
release of OTS/9000. Past releases have been spaced about 9
months apart.
The next OTS/9000 will be available Q4 1992 and based on HP_UX 9.0.
Major addition will be Connectionless Transport Service (CLTS).
Other additions will be Configurable X25 Protocol ID for Transport
class 0, 2, 4 over CONS, Configurable Link Level SAP (LSAP) for
Transport class 4 over LAN.
FDDI support on Novas and ISD ACC X25 card support are also planned
but should not be considered as commited for the HP_UX 9.0 release.
...................................................................